home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000421_news@columbia.edu_Fri Sep 22 19:53:27 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA20057
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Fri, 22 Sep 1995 15:53:33 -0400
Received: by apakabar.cc.columbia.edu id AA12490
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 22 Sep 1995 15:53:32 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Assorted Problems with C-Kermit 5A(191) for OS/2
Date: 22 Sep 1995 19:53:27 GMT
Organization: Columbia University
Lines: 49
Message-Id: <43v47n$c67@apakabar.cc.columbia.edu>
References: <DF9L2F.5tE@physics.purdue.edu>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <DF9L2F.5tE@physics.purdue.edu>,
Andrew J. Korty <korty@london.physics.purdue.edu> wrote:
>We've been having some problems with OS/2 C-Kermit when a file
>transfer goes bad or a COM port gets hung.
>
>If a file transfer fails (because the line goes down or some other
>irregularity), it seems impossible to hang up the line without
>physically disconnecting the phone line. The "hangup" command doesn't
>cut it. This doesn't happen very often, but when it does, shouldn't I
>be able to tell C-Kermit just to make the modem go on-hook?
This is not a Kermit problem but a modem configuration issue. Configure
your modem to drop hangup when DTR drops.
>As for the hung COM port problem, it makes it impossible to close
>C-Kermit. Not only does C-Kermit lock up so that I can't type "exit,"
>but it won't even close when I double-click the icon box, or even when
>I try to kill it with a utility like Watchcat. The only way out of
>this problem seems to be to reboot.
If an OS/2 program hangs because it has failed in a device driver call, i.e.
the device driver never returns, OS/2 will not terminate the program because
doing so would destabalize the rest of the system.
The problem is in your Device Driver. If you are using the one that shipped
with your version of OS/2 and have not applied service packs, do so.
If you are using an alternate driver, contact the author and make sure you
are using the latest version.
Most driver hangs on ISA machines are caused by interrupt conflicts. Make
sure that your Serial port IRQs are not also being used by Sound Boards,
network cards, scsi cards, etc.
>What am I doing wrong?
>
>Thanks,
>Andy
>--
>Andrew J. Korty
>Systems Programmer
>Physics Computer Network
>Purdue University
Jeffrey Altman * PO Box 220415 * Great Neck, NY * 11022-0415 * (516) 466-5495
NEW: OS/2 C-Kermit 5A(191):
ftp://kermit.columbia.edu/kermit/archives/cko191.zip
http://www.columbia.edu/kermit/cko191.html